Service authorization handshake

ABSTRACT

The present document describes systems and methods that authorize client resources such as computers, servers, computing appliances, and virtual machines to access online services provided by an online service provider. To authorize a client resource, a client submits a registration request on behalf of the client resource to an authorization service provided by the service provider. The authorization service returns an activation code to the client. The activation code may expire after an amount of time, or upon first use. The client provides the activation code to an agent running on the client resource. The agent establishes communication with the authorization service, and upon providing the activation code to the authorization service, receives an authorization token that can be used by the client resource to access online services in accordance with security roles or permissions specified with the registration request.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.14/984,957, filed Dec. 30, 2015, entitled “SERVICE AUTHORIZATIONHANDSHAKE,” the disclosure of which is hereby incorporated herein in itsentirety.

BACKGROUND

Online services are an important part of modern computing. Onlineservices provide storage and backup services, data processing services,key management services, virtual computing services, financial services,shopping services, and many other computing and data access services.Access to online services is generally controlled by a variety ofauthentication and authorization techniques such as username/passwordpairs, digital certificates, network address filters, and biometricidentification. When accessing an online service, a client provides theappropriate authentication information to the online service, and theonline service grants access. In some environments, clients operate avariety of client resources such as client computers, servers, virtualmachines, and other network-connected computing appliances that wouldbenefit from access to online services. However, providing clientresources access to online services can be a difficult problem.

Client resources may require different levels of access to onlineservices than would be provided by simply providing the clientcredentials to the client resource. In addition, if a client resourcerequires access to multiple online services, multiple sets of clientcredentials may be necessary. If a particular client credentials arechanged, client resources that use the particular credentials will needto be updated with the new credentials. For these and other reasons,controlling the authorization of client resources to use online servicescan be very troublesome.

BRIEF DESCRIPTION OF THE DRAWINGS

Various techniques will be described with reference to the drawings, inwhich:

FIG. 1 shows an illustrative example of an environment in which variousembodiments may be practiced;

FIG. 2 shows an illustrative example of a client resource accessing anumber of online services with a common authorization token, inaccordance with an embodiment;

FIG. 3 shows an illustrative example of a cloned client resourceaccessing an online service, in accordance with an embodiment;

FIG. 4 shows an illustrative example of an authorization service thatauthorizes access to an online service by a client resource, inaccordance with an embodiment;

FIG. 5 shows an illustrative example of a process that, as a result ofbeing performed by a service management console, an authorizationservice, and an authorization agent, authorizes access to an onlineservice by a client resource, in accordance with an embodiment;

FIG. 6 shows an illustrative example of a process that, as a result ofbeing performed by an authorization service, an authorization agent, andan online service, fulfills online service requests submitted by aclient resource, in accordance with an embodiment;

FIG. 7 shows an illustrative example of a process that, as a result ofbeing performed by an authorization service, an authorization agent, andan online service, refreshes an authorization token used by a clientresource, in accordance with an embodiment;

FIG. 8 shows an illustrative example of a process that, as a result ofbeing performed by an authorization service, registers a client resourceto use an online service, in accordance with an embodiment;

FIG. 9 shows an illustrative example of a process that, as a result ofbeing performed by an authorization agent on a client resource,activates a client resource to use an online service, in accordance withan embodiment;

FIG. 10 shows an illustrative example of a process that, as a result ofbeing performed by an authorization service, fulfills a resourceactivation request, in accordance with an embodiment;

FIG. 11 shows an illustrative example of a process that, as a result ofbeing performed by an authorization service, refreshes an activationtoken, in accordance with an embodiment; and

FIG. 12 illustrates an environment in which various embodiments can beimplemented.

DETAILED DESCRIPTION

The current document describes an authorization service that allowson-premises client resources such as servers, computing appliances, andvirtual machines to register with an online service provider, andreceive an authorization token that can be used to access onlineservices provided by the online service provider. This can allow, forexample, the on-premises client resources to communicate with, includingreceiving commands from, the online service provider. A client such asan administrator or other authorized user accesses the authorizationservice using a client computer system via an application programminginterface (“API”), command line interface, or other user interface. Theclient registers a client resource with the authorization service byproviding a resource identifier (“Resource ID”), and a security role ora set of privileges to be granted to the client resource. Theauthorization service records the resource ID and the granted role orprivileges in a resource registration database, and generates aone-time-use activation code which is returned to the client. Theone-time-use activation code expires after an amount of time.

The client authorizes the client resource by installing an authorizationagent on the client resource, and activating the authorization agentwith the authorization service. The client is provided with installationinstructions for the authorization agent along with the one-time-useactivation code. In some environments, the client is prompted todownload and execute an installation program on the client resource. Theinstallation program may take the form of an MSI, PKG, ZIP, or setup.exefile.

Once the authorization agent is installed the client activates theauthorization agent by submitting an activation command to theauthorization agent. In some implementations, the activation command issubmitted as a parameter to the installation program. The clientprovides the resource ID and the activation code as parameters with theactivation command. As a result of receiving the activation command, theauthorization agent generates and retains a public-private key pair forsigning requests sent to the authorization service. The authorizationagent generates an activation request that includes the resource ID, theactivation code, and the public key of the public-private key pair. Insome implementations, the activation request includes a pseudo-uniqueresource ID. The pseudo-unique resource ID is generated by the clientresource to have a value that tends to be unique for each instance of aclient resource, even when the client resource is imaged or cloned fromanother client resource. For example, the pseudo-unique resource ID canbe based at least in part on a processor ID, hardware serial number, ornetwork address associated with the client resource. The pseudo-uniqueresource ID may be used to detect client resources that are cloned orreplicated. The authorization agent signs the activation request withthe private key of the public-private key pair and submits theactivation request to the authorization service.

The authorization service receives the activation request from theauthorization agent, and verifies the signature on the activationrequest using the included public key. The activation request isvalidated by confirming that the activation code is valid for theprovided resource ID, is not expired, or already in use. If theactivation request is valid, the authorization service records that theactivation code is no longer valid in a database maintained by theactivation service and records the client resource information in adatabase of authorized client resources. The activation code may beinvalidated by the authorization service itself, or by causing anotherentity to invalidate the activation code. The authorization serviceretrieves the requested roll or privileges from the resourceregistration database based at least in part on the resource ID providedwith the activation command. The activation service contacts the onlineservice provider, and acquires an authorization token that provides therequested role or privileges. The authorization service returns theauthorization token to the authorization agent running on the clientresource. A resource authorization database retains information relatingto issued authorization tokens for later use.

The authorization agent uses the authorization token to access onlineservices provided by the online service provider. When the clientresource sends a request to an online service, the client resourceprovides the authorization token with the request. The online servicereceives the request, and fulfills or denies the request in accordancewith the role or privileges associated with the authorization token. Ifthe authorization token expires, the authorization token may berefreshed by the authorization agent. To refresh an authorization token,the authorization agent sends a signed request to the authorizationservice. The authorization service validates the digital signature onthe request, acquires a new authorization token from the online serviceprovider, and returns the new authorization token to the authorizationagent.

In some environments client resources may be cloned or replicated.Cloned resources may be detected by the authorization service duringactivation, or during requests for service. In some implementations, theauthorization agent generates a pseudo-unique resource identifier thatis provided to the authorization service during registration of theclient resource. The pseudo-unique resource identifier is provided tothe authorization service during registration and distinguishes a clonedclient resource from a related parent client resource. In anotherimplementation, the authorization agent includes a sequence number witheach request to the authorization service. If the authorization servicereceives a request from a client resource that includes a previouslyreceived resource ID and sequence number, a cloned resource is detected.

Various authentication mechanisms used by a client may be used toacquire authorization tokens for client resources. For example, if aclient uses a username and a password to authenticate with an onlineservice. The username and password can be supplied by the client duringthe registration of a client resource with the authorization service. Ifthe client uses a digital certificate to authenticate with the onlineservice, the digital certificate can be supplied by the client duringthe registration of the client resource with the authorization service.

Client resources may be located on a local client computer system, aclient-controlled network environment, on-premises data center, remotenetwork, or network controlled by the online service provider.On-premises client resources refer to client resources that arephysically located at the client's place of business, and are subject tothe physical control of the client. The authorization service may be aseparate service offered by the online service provider, or maybe aservice associated with a particular online service offered by theonline service provider. In some implementations, the authorizationservice is offered by a third-party, and the authorization servicecoordinates with the online service provider or the particular onlineservices for which the authorization service provides authorizationtokens. By distributing authorization tokens to client resources, clientresources are able to access a number of online services under theauthority of the client that owns the client resources withoutdistributing client credentials to the client resources or issuing newcredentials for each client resource.

FIG. 1 shows an illustrative example of an environment 100 in whichvarious embodiments may be practiced. An online service provider 102provides a number of online services as well as an authorization service104. A client 106 of the online service provider 102 accesses theservices provided by the online service provider via a computer network.The client 106 manages access to the online service provider from aclient computer system 108 that provides a service management console110. The client 106 owns and operates a number of client resources suchas servers, virtual machines, and other computing appliances on thenetwork.

If the client 106 wants to provide access to the services provided bythe online service provider to a client resource 112, the clientgenerates a registration request using the service management console110 and sends the registration request to the authorization service 104.The registration request includes a resource ID for the client resource112, a security role for to be granted to the client resource, and anycredentials associated with the client 106 that are necessary toauthorize the request such as a username/password combination or aclient digital certificate.

The authorization service 104 generates an activation code, and storesthe activation code, resource ID, and a timestamp in a resourceregistration database located within the authorization service 104.Storing the activation code in the resource registration database mayinclude storing a record with the activation code itself or informationthat enables verification of access to the activation code, such as ahash or other information derived based at least in part on theactivation code. The resource ID may be stored as a hash that allowsverification of a matching resource ID presented by the authorizationagent. The activation code is returned to the client by the servicemanagement console 110, and the client 106 is provided with instructionsfor downloading and installing an authorization agent 114 onto theclient resource 112. In some embodiments, the authorization servicecauses the authorization agent 114 to be installed on the clientresource 112 without intervention from the client 106. The authorizationservice 104 commands the service management console 110 to contact theclient resource 112 and install the authorization agent 114. In anotherembodiment, the client 106 received instructions from the authorizationservice 104, and downloads an installation program for the authorizationagent that is compatible with the client resource 112. The installationprogram can be transferred to the client resource 112 over the computernetwork or by using computer readable media such as a CD-ROM, USB memorystick, flash drive, or other media. The client 106 executes theinstallation program on the client resource 112 to install theauthorization agent 114. Parameters may be provided to the installationprogram that specify the activation code and the resource ID. In someimplementations, the client 106 issues an activation command to theauthorization agent that includes the resource ID and the activationcode as parameters.

The authorization agent 114 activates by sending an activation requestthat includes the activation code to the authorization service 104. Insome implementations, the authorization agent 114 generates apublic-private key pair such as a 2048 bit RSA key pair for use insigning requests sent to the authorization service 104. Theauthorization agent 114 may also generate a pseudo-unique resource IDthat is supplied with the resource ID to the authorization service 104.The pseudo-unique resource ID helps to ensure that client resources thatare generated by cloning or replicating other client resources haveunique identifiers with the authorization service 104. The authorizationagent 114 generates an activation request that includes the resource ID,the activation code, and optional pseudo-unique resource ID, and thepublic key of the public-private key pair. The activation request issigned using the private key of the public-private key pair and sent tothe authorization service 104.

The authorization service 104 receives the activation request andverifies the signature on the request using the public key provided withthe request. If the activation request is not properly signed, therequest is denied. If the activation request is properly signed, theauthorization service 104 accesses the resource registration databaseand extracts the activation code associated with the provided resourceID. If the activation code is not found, or if the activation code isexpired, or if the activation code is not associated with the providedresource ID, or if the activation code has already been used, theactivation code is invalid and the activation request is denied. If theactivation code is valid, the activation code is removed from theresource registration database so that the activation code can no longerbe used, and the roles and/or privileges assigned to the client resource112 are retrieved from the registration database. The authorizationservice 104 requests an authorization token from the online serviceprovider 102 that provides the roles and/or privileges assigned to theclient resource 112. The authorization token, the resource ID, thepseudo-unique resource ID, the public key of the public-private keypair, and a current timestamp are retained in a resource authorizationdatabase within the authorization service 104. The authorization service104 returns the authorization token to the authorization agent 114.

The authorization agent 114 receives the authorization token which canbe used to access online services provided by the online serviceprovider 102. In some implementations, the authorization agent 114provides service API to applications running on the client resource 112.Service requests received by the service API are passed on to a serviceprovided by the online service provider 102 along with the authorizationtoken. The online service uses the authorization token to identify therequester, and to identify the role or permissions granted to therequester. If the role or permissions granted to the requester allow theservice request to be fulfilled, the service fulfills the request andprovides a response to the authorization agent 114. In anotherimplementation, the authorization agent 114 provides the authorizationtoken to applications running on the client resource 112, and theapplications submit requests to a service provided by the online serviceprovider 102 by providing the authorization token with the servicerequests. The service uses the authorization token to identify andauthorize the requester, fulfills the service requests as appropriate,and provides associated responses for the service requests to theapplication.

In various implementations, the authorization token may be configured toexpire after an amount of time. For example, the authorization token mayexpire one hour after the authorization token has been issued to theauthorization agent 114. The authorization service 104 may issue anupdated token to the authorization agent 114 in anticipation ofexpiration of the authorization token, as a result of receiving arefresh command from the authorization agent 114, or as a result ofreceiving a request from the authorization agent 114 (or applicationrunning on the client resource) with an expired authorization token.

FIG. 2 shows an illustrative example of a client resource accessing anumber of online services with a common authorization token, inaccordance with an embodiment. An environment 200 includes a clientresource 202 that accesses a number of online services provided by anonline service provider 204. The client resource 202 has anauthorization agent 206 installed that, in response to an activationrequest that includes an activation code, receives an authorizationtoken from an authorization service 208. The authorization service 208is associated with the online service provider 204. The online serviceprovider 204 provides a number of online services including a computingservice 210, a storage service 212, and a cryptography service 214. Inadditional implementations, the online service provider 204 may provideother online services such as key management services, virtual computingservices, email services, messaging services, videoconferencingservices, or Web search services. The authorization token provided bythe authorization service 208 is associated with one or more rolesand/or one or more permissions that grant access to one or more of theonline services provided by the online service provider 204. Based atleast in part on the roles and permissions associated with theauthorization token, the authorization token may be used by theauthorization agent 206 to access one or more of the services providedby the online service provider 204.

For example, if a client registers the client resource 202 with theauthorization service 208 and specifies that the client resource 202 begranted a role that is permitted to access a number of services providedby the online service provider 204, the authorization token provided bythe authorization service 208 to the authorization agent 206 on theclient resource 202 may be used by the client resource 202 to access anyservice on the online service provider 204. For example, in FIG. 2, theauthorization token provided by the authorization service 208 may beused by the authorization agent 206 to access the computing service 210,the storage service 212 or the cryptography service 214. The client,when authorizing the client resource, may request access to one, all, ora subset of the services provided by the online service provider. Inanother example, the authorization agent 206 receives a restricted tokenfrom the authorization service 208. The restricted token may be used bythe authorization agent 206 to access the computing service 210 and thestorage service 212, but not the cryptography service 214.

In some implementations, the client resource 202 receives commands froma service provided by the online service provider 204. For example, thetoken provided by the authorization agent 206 may allow access to arun-command service. The run-command service sends commands to theclient resource 202 to execute. In another example, a security serviceprovided by the online service provider 204 may determine that theclient resource 202 has been compromised and send a command by theauthorization agent 206 that causes a client resource 202 to deletesensitive data stored on the client resource 202.

FIG. 3 shows an illustrative example of a cloned client resourceaccessing an online service, in accordance with an embodiment. A system300 includes an online service provider 302 that provides anauthorization service 304 and a computing service 306. In additionalembodiments, the online service provider 302 may provide web hostingservices, storage services, or other services in place of the computingservice 306. A client resource 308 such as a virtual computer instance,web appliance, or other computing device hosts an authorization agent310. The authorization agent 310 is registered with the authorizationservice 304, and has been provided with an authorization token by theauthorization service 304. The client resource 308 generates and sendsrequests to the computing service 306 using the authorization token.Based at least in part on the authorization token, the computing service306 determines whether the request is authorized and fulfills therequest.

If the client resource 308 is cloned, copied, or otherwise replicated, acloned client resource 312 is created. The cloned client resource 312includes a duplicate authorization agent 314. In some implementations,the cloned client resource 312 and the duplicate authorization agent 314have a configuration that matches the configuration of the clientresource 308 and the authorization agent 310. If the duplicateauthorization agent 314 generates and submits a service request to thecomputing service 306 that includes an authorization token that matchesthe authorization token used by the authorization agent 310, thecomputing service 306 detects that matching authorization tokens arebeing used by two different client resources and denies the servicerequest submitted by the cloned client resource.

In some embodiments, the computing service 306 detects that matchingauthorization tokens are being used by using a pseudo-unique resourceidentifier provided by the client resources. The authorization agentsgenerate pseudo-unique resource identifiers that are based at least inpart on a processor ID, the network address of network interfacesassociated with the client resources, or a machine serial number. Theauthorization agents provide the pseudo-unique resource identifier whensubmitting requests to the computing service 306. In another embodiment,the computing service 306 detects that matching authorization tokens arebeing used by examining sequence numbers included with requests sent bythe authorization agents. Requests generated by an authorization agentare assigned a sequence number by the authorization agent. The sequencenumber is incremented for each successive request, and the computingservice 306 compares the sequence number of each request received from agiven authorization agent to the sequence number of the previous requestreceived from the given authorization agent. If the computing service306 receives a request from a duplicate authorization agent with aresource ID and a sequence number that match another request sent by theclient resource 308, the computing service 306 will determine that therequest originated from the cloned client resource 312 from a clonedresource. The computing service 306 notifies the authorization service304, and the authorization service 304 reissues a new authorizationtoken to the cloned client resource 312. In some implementations, whenthe computing service determines that the request originated from thecloned client resource 312, the service request is denied and a newtoken is not issued to the cloned client resource.

In another embodiment, the duplicate authorization agent 314 detectsthat the cloned client resource 312 is a cloned resource by comparingthe pseudo-unique resource identifier to a newly generated pseudo-uniqueresource identifier. Prior to sending a request to the computing service306, the duplicate authorization agent 314 generates a new pseudo-uniqueresource identifier and compares the new pseudo-unique resourceidentifier to the stored pseudo-unique resource identifier copied fromthe client resource 308 when the client resource 308 was cloned toproduce the cloned client resource 312. If the stored pseudo-uniqueresource identifier does not match the new pseudo-unique resourceidentifier, the service request submitted by the cloned client requestis denied. In some implementations, if the stored pseudo-unique resourceidentifier does not match the new pseudo-unique resource identifier, theduplicate authorization agent 314 contacts the authorization service 304and requests a new authorization token. The new authorization token isused by the duplicate authorization agent 314 to request services fromthe computing service 306.

FIG. 4 shows an illustrative example of an authorization service thatauthorizes access to an online service by a client resource, inaccordance with an embodiment. A system diagram 400 includes an onlineservice provider 402 that is associated with an authorization service404. A client resource 406 is registered with the authorization service404 by a client 407 operating a client computer 408. In the exampleshown in FIG. 4, the online service provider 402 includes a computingservice 410, but the computing service 410 can optionally be replaced bya virtual computing service, a storage service, a cryptography service,or other online service. The online service provider 402 provides anauthorization token service 412. The authorization token service issuestokens to the authorization service 404 which may be used by onlineentities to authorize service requests submitted to the computingservice 410.

The authorization service 404 includes a resource authorization manager414. The resource authorization manager 414 is an operational modulethat exposes an activation API and a registration API over the network.The registration API provides functions that allow the client 407 toregister client resources that are authorized to access the onlineservice provider 402. The activation API provides functions that allowan authorization agent to receive an authorization token in exchange foran activation code provided by the client 407. The authorization service404 includes a resource registration database 418 that retainsregistration information for client resources. The registrationinformation may include a resource ID, an activation code, a securityrole, security permissions, a registration timestamp, and a resourcename. The authorization service 404 includes a resource authorizationdatabase 420. The resource authorization database 420 retainsinformation relating to activated client resources such as the clientresource 406. The information relating to activated client resources mayinclude a resource ID, a pseudo-unique resource ID, a public encryptionkey, security roles, security permissions, and a token expiration.

The client resource 406 is authorized to access the computing service410 using a process initiated by the client 407. The client 407 uses aservice management console 422 hosted by the client computer 408. Theservice management console 422 provides command line interface,application programming interface, graphical user interface, or otherinterface to the resource authorization manager 414. The client 407submits a client-resource registration request to the resourceauthorization manager 414 to register the client resource 406. Theclient-resource registration request specifies one or more securityroles and/or one or more permissions to be granted to the clientresource 406. The client-resource registration request is authorized bythe client 407 using credentials of the client 407. For example, theclient 407 may authorize the client-resource registration request usingthe client's username and password, digital certificate, or biometricsignature. The resource authorization manager 414 verifies thecredentials provided by the client 407, and if the credentials aresufficient, generates an activation code. In some implementations, theactivation code expires after an amount of time. The amount of time isdetermined as an amount of time adequate to complete the activation ofthe client resource 406, such as an hour. The activation code and theexpiration are stored in the resource registration database 418. Theresource authorization manager 414 returns the activation code to theclient 407 by the service management console 422.

The resource authorization manager 414 causes an authorization agent 424to be installed on the client resource 406. In some implementations, theresource authorization manager 414 provides the client 407 withinstructions on how to download and install the authorization agent 424onto the client resource 406. In another implementation, the resourceauthorization manager 414 sends commands to the service managementconsole 422 to cause the service management console 422 to install theauthorization agent 424 on the client resource 406. In yet anotherimplementation, the resource authorization manager 414 sends commands tothe client resource 406 that cause the client resource 4062 install theauthorization agent 424. The authorization agent 424 may be installed bycopying executable images onto the client resource 406, or by running aninstallation program or installation script for the authorization agent424 on the client resource 406. In some implementations, the client 407provides the resource identifier and the activation code as parametersto the installation program or script that installs the authorizationagent 424. In another implementation, the client 407 sends the resourceID and the activation code to the authorization agent 424 as part of anactivation command.

The authorization agent 424 operates as a service on the client resource406, and activates with the resource authorization manager 414 toacquire an authorization token that allows access to the computingservice 410. The authorization agent 424 generates a public-private keypair, and retains the public-private key pair on the client resource406. In some implementations, the authorization agent 424 generates apseudo-unique resource ID that may be used to detect whether clientresources are cloned or replicated. The authorization agent 424 sends anactivation request to the authorization service that includes theresource ID for the client resource, the pseudo-unique resource IDgenerated by the authorization agent 424, the public key of thepublic-private key pair, and a timestamp. The activation request issigned using the private key of the public-private key pair, and sent tothe authorization service 404. The authorization service 404 accessesthe resource registration database 418 and determines whether theactivation code is valid for the provided resource ID, and whether theactivation code has expired or been previously used. If the activationcode is not been previously used, is not expired, and is valid for theprovided resource ID, the resource authorization manager 414 accepts theactivation of the authorization agent 424 and records the resource ID,the pseudo-unique resource ID, the roles and permissions granted to theclient resource 406, and the public key of the public-private key pairin the resource authorization database 420. The resource authorizationmanager 414 requests an authorization from the authorization tokenservice 412 that grants the roles and permissions requested during theregistration of the client resource 406, and returns the authorizationtoken to the authorization agent 424.

The client resource 406 may use the authorization token to authorizerequests sent to the computing service 410. In some implementations, theauthorization token expires after an amount of time, such as an hour. Ifthe authorization token expires, the authorization agent 424 may requesta refreshed token from the resource authorization manager 414. Requestsfrom the authorization agent 424 are signed with the private key of thepublic-private key pair, and the resource authorization manager 414verifies the source of the requests by confirming the signature on therequest with public keys stored in the resource authorization database420. The client 407 is able to manage roles and permissions granted toclient resources via the service management console 422. For example, ifa particular client resource is compromised or decommissioned, theclient 407 can access the resource authorization manager 414 via theservice management console 422 and unregister the compromised clientresource. The resource authorization manager 414 will contact theauthorization token service 412 and invalidate the tokens held by thecompromised resource. As a result, the compromised resource will nolonger be able to access the computing service 410.

FIG. 5 shows an illustrative example of a process that, as a result ofbeing performed by a service management console, an authorizationservice, and an authorization agent, authorizes access to an onlineservice by a client resource, in accordance with an embodiment. A swimdiagram 500 illustrates operations performed by the service managementconsole, the authorization service, and the authorization agent. Theservice management console is an interface program used by a client tocommunicate with the authorization service. The service managementconsole may be a command line interface, a graphical interface, or anAPI. The process begins at block 502, with a client submitting, via theservice management console, a request to register a client resource tothe authorization service. The request includes a number of parametersincluding a name for the client resource, and a security role and/orsecurity permissions to be granted to the client resource. The securityrole and/or security permissions specify the rights that the clientresource will have when accessing the online service.

At block 504, the authorization service receives the request from theservice management console. The authorization service examines theclient credentials which are included with the request to determinewhether to register the client resource for the requested security roleand/or security permissions. For example, the client may provide ausername and password, a digital certificate, or a biometric signaturethat identifies the client and allows the authorization service toauthorize the request. If the request is authorized, execution proceedsto block 508. The authorization service generates an activation code anda resource ID for the client resource, and the activation code, theresource ID, and a registration timestamp are added to the resourceregistration database. In some implementations, the activation code is aone-time-use alphanumeric code that expires after an amount of time oras a result of first use. The expiration may be configured by theauthorization service on a per client resource basis or globally forclient services authorized by the authorization service. The expirationcan be recorded in the form of a timestamp representing the current timetogether with an offset amount of time, or as a timestamp representing atime in the future when expiration will occur. The client may specify anexpiration for the activation code with a registration request. If theclient specifies an expiration with the registration request theexpiration is recorded in the resource registration database on theauthorization service. The authorization service returns the activationcode and the resource ID to the service management console.

At block 510, the service management console receives the activationcode and the resource ID from the authorization service. As a result ofreceiving the registration information from the authorization service,the service management console initiates installation 512 of theauthorization agent on the client resource. In some implementations, theauthorization service provides instructions with the activation codewhich instruct the client to install an authorization agent on theclient resource. The instructions may include an installation program orscript for the authorization agent, or instructions for downloading andinstallation program or script for the authorization agent. Theinstallation program or script takes, as parameters, the registrationinformation provided by the authorization service. In anotherimplementation, the authorization service causes the service managementconsole to launch a script that copies an executable image of theauthorization agent to the client resource, and launches theauthorization agent on the client resource. In yet anotherimplementation, the authorization service causes the service managementconsole to launch an installation program on the client resource thatinstalls and runs the authorization agent.

At block 514, the authorization agent is installed on the clientresource. As part of the installation, the registration informationprovided by the authorization service to the service management consoleis passed to the authorization agent. The authorization agent retainsthe resource ID and the activation code for use in activating with theauthorization service. The authorization agent generates 515 acryptographic public-private key pair. The public-private key pair isstored by the authorization agent on the client resource, and the publickey of the public-private key pair is provided to the authorizationservice. The authorization agent signs future requests sent to theauthorization service using the private key of the public-private keypair. At block 516, the authorization agent activates with theauthorization service by providing the resource ID, the public key, andthe activation code to the authorization service. The activation requestmay be signed with the private key of the public-private key pair. Insome implementations, the authorization agent generates a pseudo-uniqueresource ID based at least in part on a processor ID, hardware serialnumber, network address, IP address, or media access code (“MAC”) of anetwork interface associated with the client resource. The pseudo-uniqueresource ID is provided to the authorization service during activationand may be used to differentiate between resources that are cloned orreplicated during an imaging or snapshot process.

At block 518, the authorization service receives the activation requestand confirms the signature on the request using the public key providedwith the request. The authorization service confirms the activation codeand resource ID using information in the resource registration database.Activation of the client resource is granted if the activation token isnot expired, has not been previously used, and is registered to theprovided resource ID. If activation is granted, the authorizationservice registers 519 the client resource with the online service byacquiring an authorization token from an authorization token serviceassociated with the online service. The authorization token grants thesecurity roles and/or security permissions for which the client resourceis registered when provided with a service request to the onlineservice. At block 520, the authorization token is provided to theauthorization agent. The authorization agent receives the authorizationtoken from the authorization service, and stores 522 the authorizationtoken for use with service requests submitted to the online service.

In some implementations, at block 516, the authorization agent generatesa public-private key pair. The public-private key pair is retained bythe authorization agent for use in signing messages exchanged betweenthe authorization agent on the authorization service. The public key ofthe public-private key pair is provided to the authorization servicewith the activation code and resource ID, in a message signed with theprivate key of the public-private key pair. At block 518, theauthorization service confirms the signature using the provided publickey and retains the public key in a resource authorization databasemaintained by the authorization service. Messages sent by theauthorization service to the authorization agent may be signed with thepublic key. For example, when the authorization service sends theauthorization token to the authorization agent at block 520, theauthorization token may be encrypted using the public key, and theauthorization agent may decrypt the message using the private key of thepublic-private key pair.

FIG. 6 shows an illustrative example of a process 600 that, as a resultof being performed by an authorization service, an authorization agent,and an online service, fulfills online service requests submitted by aclient resource, in accordance with an embodiment. A swim diagram 700illustrates operations performed by the authorization service, theauthorization agent, and the online service. The authorization service,as a result of the process illustrated in FIG. 5, issues 602 andauthorization token to the authorization agent running on the clientresource. The authorization agent stores 604 the authorization token foruse with service requests submitted to the online service. At block 606,the authorization agent generates a service request for the onlineservice. The service request is submitted 608 to the online servicealong with the authorization token.

As a result of receiving the service request, the online serviceauthenticates 610 the requester by at least in part determining that thetoken is valid and not expired. If the resource ID is provided by theauthorization agent, the authorization agent determines that theauthorization token is associated with the resource ID. At block 612,the online service retrieves the security role and/or securitypermissions associated with the authorization token. If the securityrole and/or security permissions are sufficient to fulfill the request,execution proceeds to block 614 and the online service fulfills therequest submitted by the client resource. If the authorization token isnot valid, or if the security role or security permissions areinsufficient, the service request is denied.

At block 616, the authorization agent receives the results of theservice request. If the service request was fulfilled, the results maybe passed to the originator of the service request such as anapplication program running on the client resource. If the servicerequest was denied, the authorization agent may take further actionssuch as requesting renewal of the authorization token or reregisteringthe client resource with the authorization service.

FIG. 7 shows an illustrative example of a process that, as a result ofbeing performed by an authorization service, an authorization agent, andan online service, refreshes an authorization token used by a clientresource, in accordance with an embodiment. In many implementations,authorization tokens that are issued to authorization agents expireafter a period of time and are refreshed by the authorization agent inorder to secure further access to the online service. A swim diagram 700illustrates operations performed by the authorization service, theauthorization agent, and the online service. At block 702, theauthorization agent generates a service request for the online service.The service request may originate with the authorization agent, or maybe generated in response to a request from an application programrunning on the client resource. The authorization agent submits 704 theservice request to the online service, along with the authorizationtoken.

The online service attempts to authenticate 708 the service request byconfirming that the token is validly registered to the client resource,and that any credentials or signatures associated with the servicerequest are valid. At block 710, the online service determines that theauthorization token has expired, and notifies the authorization agent.

The authorization agent receives the notification that the authorizationtoken is expired, and requests 712 a new authorization token from theauthorization service. The authorization agent signs the request with aprivate key of a public-private key pair generated by the authorizationagent, and used during the registration of the client resource with theauthorization service.

As a result of receiving the request for a new authorization token, theauthorization service authenticates 713 the request by validating thesignature on the request using the public key of the public-private keypair maintained in the resource authorization database, and acquires 714a new authorization token. The new authorization token may be acquiredby retrieving the security roles and/or security permissions from theresource registration database and requesting an authorization tokenfrom an authorization token service associated with the online serviceused by the client resource. At block 716, the authorization serviceprovides the new authorization token to the authorization agent. The newauthorization token may be signed or encrypted using the public key ofthe public-private key pair, and decrypted by the authorization agentupon receipt.

The authorization agent receives the new authorization token from theauthorization service, and stores 718 the new authorization token foruse in submitting service requests to the online service. The servicerequest is resubmitted 720 the online service by the authorization agentalong with the new authorization token. Service requests may besubmitted to the online service using a secure network protocol such asTLS or SSL on an IP port designated for receiving such requests.

The online service receives the resubmitted service request andauthenticates 722 the resubmitted request using the new authorizationtoken. If the new authorization token is associated with a security roleand/or security permissions that allow the request to be fulfilled, theonline service fulfills 724 the service request and returnscorresponding results to the authorization agent.

In some implementations, the authorization agent generates apseudo-unique resource ID that is provided to the authorization servicewhen requesting a new authorization token. The pseudo-unique resource IDmay be used by the authorization service to detect whether theauthorization agent is installed on a client resource that is clonedfrom another client resource which was previously registered with theauthorization service. If a cloned client resource is detected, theauthorization service may register the cloned client resource is a newclient resource rather than refreshing the token currently used by thecloned client resource. In some implementations, when a cloned clientresource is detected, the authorization service denies the request for anew authorization token, causing the authorization agent on the clonedclient resource to issue a request to register as a new client resource.

In another implementation, at block 702, the authorization agentgenerates a service requests sequence number for the service request.The service requests sequence number is incremented for each successiverequest submitted to the online service. At block 708, when the onlineservice receives a service request containing a sequence number, theonline service compares the received sequence number to the previouslyreceived sequence number. If the received sequence number is not greaterthan the previously received sequence number, the online servicedetermines that the requester is a cloned client resource, and deniesthe service request. If the authorization agent receives notificationfrom the online service of incorrect sequence number, the authorizationagent may take several actions including sending a request to theauthorization service to invalidate the current authorization token,requesting a new authorization token from the authorization service, andreporting the cloned resource to the client via the service managementconsole.

FIG. 8 shows an illustrative example of a process that, as a result ofbeing performed by an authorization service, registers a client resourcefor use with an online service, in accordance with an embodiment. Aprocess diagram 800 shows a process that begins at block 802 with anauthorization service receiving a registration request from a client toregister a client resource. The registration request may originate froma client computer that hosts a service management console. The clientaccesses the service management console from the client computer togrant or deny access to online services from various client resources.The registration request can include a resource name, and specifies oneor more security roles and/or one or more security permissions. Thesecurity roles and permissions define rights and privileges to begranted to the client resource with respect to the online service. Forexample, a security role may grant the client resource administrativeaccess rights to the online service, or privileges may be specifiedwhich grant the client resource the ability to execute a read commandfrom a storage service but deny the ability to execute a write commandto the storage service. The registration request includes a credentialsupplied by the client. The credentials may take the form of a usernameand password, digital certificate, two factor authentication sequence,biometric identification, or other credential. At block 804, theauthorization service verifies the client's credentials to authenticatethe client's identity. The authorization service determines 806 whetherthe client is authorized to register a client device with the requestedsecurity roles and/or privileges based at least in part on the client'scredentials. In some implementations, the client credentials include aproperty (AssignRole) that indicates whether the client may assign rolesand privileges to client resources. If the client's credentials do notallow the client to register a client resource with the requestedsecurity roles and/or privileges, execution advances to block 808 andthe registration request is denied.

If the client's credentials permit the client to register the clientresource, execution advances to block 810 and the authorization servicegenerates a resource ID for the resource. The resource ID is anidentifier that is returned to the client and supplied to the clientresource when the client resource is activated. The resource ID may bean alphanumeric sequence, an integer, a generally unique identifier(“GUID”), a binary sequence, or database index. At block 812, theauthorization service generates an activation code for the resource. Insome implementations, the activation code is an alphanumeric sequencesuch as a group of four tuples, an integer, or a sequence of charactersthat produce a set of phonetically pronounceable syllables. For example,the activation code may be a 128 bit base 64 encoded (22 characters)activation code generated using a random or pseudorandom number. Theauthorization service stores 814 the resource ID and activation codealong with the resource name and security roles in a resourceregistration database maintained by the authorization service. In someimplementations, the authorization service stores the timestamp thatrecords the time the activation code was generated, and the activationcode expires after an amount of time, such as an hour.

At block 816, the authorization service returns the activation code andthe resource ID to the client. In some implementations, theauthorization service returns the activation code and the resource ID tothe client via the service management console. The authorization servicemay cause the service management console to install an authorizationagent on the client resource. Alternatively, the authorization servicemay provide instructions to the client for downloading and installing anauthorization agent on the client resource.

FIG. 9 shows an illustrative example of a process that, as a result ofbeing performed by an authorization agent on a client resource,activates a client resource to use an online service, in accordance withan embodiment. A process diagram 900 illustrates a process that beginsat block 902 with an authorization agent requesting to activate a clientresource, for example by being commanded by a client. The authorizationagent may be commanded to activate the client resource during theprocess by which the authorization agent is installed on the clientresource. For example, the installation program or installation scriptthat installs the authorization agent may take parameters that includean activation code and resource ID. Once the agent is installed, theinstallation script or installation program initiates the activationprocess illustrated in FIG. 9. In another example, the client installsthe authorization agent, and then the client executes an activationcommand via an interface provided by the authorization agent, providingthe activation code and resource ID as parameters.

As a result of receiving the command to activate a client resource, theauthorization agent creates 904 a pseudo-unique resource ID. Thepseudo-unique resource ID may be generated based at least in part on aserial number associated with the client resource, a processor ID, anetwork address of a network interface associated with the clientresource, a media access control (“MAC”) address of a network interfaceassociated with the client resource, or system configuration of theclient resource. The pseudo-unique resource ID may be used todifferentiate client resources that are cloned using image files orsnapshots from their parent client resources or other cloned clientresources. At block 906, the authorization client generates and stores apublic-private key pair such as a 2048-bit RSA key pair. Thepublic-private key pair is used to communicate with an authorizationservice.

The authorization agent generates 908 an activation command to besubmitted to an authorization service. The activation command mayinclude, for example, the resource ID, the pseudo-unique resource ID,the activation code, and the public key of the public-private key pair.The activation command is signed 910 using the private key of thepublic-private key pair. At block 912, the activation command istransmitted to the authorization service. The activation command may betransmitted to the authorization service over the network using a secureprotocol such as TLS or SSL.

The authorization service returns the results of the activation commandto the authorization agent. If the authorization service indicates 914that activation was not successful, access to the online service isdenied 916. If the authorization service indicates 914 that theactivation command was successful, the authorization agent receives 918an authorization token from the authorization service that may be usedto access the online service in accordance with security roles andsecurity permissions specified by the client during registration of theclient resource. The authorization token is stored 920 by theauthorization agent for use with later service requests.

FIG. 10 shows an illustrative example of a process that, as a result ofbeing performed by an authorization service, fulfills a resourceactivation request, in accordance with an embodiment. A process diagram1000 shows a process that begins at block 1002 with an authorizationservice receiving an activation request from an authorization agentrunning on a client resource. The activation request includes anactivation code, a resource ID, a pseudo-unique resource ID, a publickey of a public-private key pair associated with the authorizationagent, and a timestamp. The activation request is signed with a privatekey of the public-private key pair. The authorization service makes anumber of determinations to determine whether the activation request isallowed or not.

At block 1003 the authorization service determines whether theactivation request is expired. The activation request is expired if thetimestamp included with the activation code is more than five minutesold. This may prevent an activation request from being reused in areplay attack. If the activation request is not expired, executionproceeds to block 1004, and the authorization service determines whetherthe signature on the activation request is correct using the public keyprovided with the authorization request. If the signature is valid, theauthorization service queries the resource registration database todetermine 1006 whether the activation code has expired. The activationcode may be expired if an amount of time greater than an expirationthreshold has expired since the activation code was issued by theauthorization service, or if the activation code was previously used toactivate a client resource with the authorization service. If theactivation code is not expired, the authorization service determines1008 whether the activation code is valid. The activation code is validif the information in the resource registration database indicates thatthe activation code was properly registered to the client resourcehosting the authorization agent. If the above conditions are not met,execution proceeds to block 1012 and the authorization service deniesthe activation request. If the above conditions are met, executionproceeds to block 1014.

At block 1014, the authorization service records the activationinformation in a resource authorization database. The activationinformation may include a timestamp indicating when the activationrequest was granted, an expiration for an authorization token associatedwith the activation, the resource ID and pseudo-unique resource ID forthe client resource, and the public key of the public-private key pair.At block 1016, the authorization service acquires the authorizationtoken for the online service. An authorization token for the onlineservice may be acquired from an authorization token service associatedwith the online service. In some implementations, the authorizationtoken service is associated with an online service provider whichprovides a plurality of online services. In such implementations, asingle authorization token may be used with the plurality of onlineservices.

At block 1018, the authorization service provides the authorizationtoken to the authorization agent. The authorization token may be signedor encrypted with the public key provided by the authorization agent aspart of the request. The authorization token may be used by theauthorization agent and the associated client resource to make servicerequests to the online service.

FIG. 11 shows an illustrative example of a process that, as a result ofbeing performed by an authorization service, refreshes an activationtoken, in accordance with an embodiment. A process diagram 1100illustrates a process for refreshing an activation token that begins atblock 1102 with an authorization service receiving a refresh requestfrom an authorization agent. The refresh request includes a timestampfor the request, a resource ID for the client resource, and in someembodiments a pseudo-unique resource ID for the client resource. Therefresh request is signed with a private key of a public-private keypair owned by the authorization agent.

The authorization service receives the refresh request and queries 1104a resource authorization database to retrieve the public key for theauthorization agent. Using the public key, the authorization servicedetermines 1106 whether the refresh request has expired. Theauthorization service determines whether the refresh request is expiredby determining whether the difference between the timestamp and thecurrent time exceeds a threshold value. In some implementations thethreshold value is five minutes. If the refresh request has expired,execution proceeds to block 1108 and the refresh request is denied. Ifthe authorization service determines that the refresh request has notexpired, execution proceeds to decision block 1110 where theauthorization service determines whether the signature on the refreshrequest is valid. If the authorization service determines that thesignature on the refresh request is not valid the authorization servicedenies 1112 the refresh request. If the authorization service determinesthat the signature on the refresh request is valid, execution proceedsto decision block 1114 where the authorization service queries theresource authorization database to determine if the authorization agentis hosted by a cloned client resource. A cloned resource may be detectedby examining the pseudo-unique resource ID. If the resourceauthorization database includes an entry for the resource ID specifiedwith the refresh request but the pseudo-unique resource ID provided withthe request does not match the pseudo-unique resource ID in the resourceauthorization database, the authorization service determines that theclient resource hosting the authorization agent may be cloned. If theauthorization service determines that the client resource may be cloned,execution proceeds to block 1116 and the authorization service deniesthe refresh request and indicates to the authorization agent that acloned resource has been detected. In some implementations, theauthorization service creates a new entry in the resource authorizationdatabase and authorizes the cloned resource with the resource IDdifferentiated from the parent client resource using the pseudo-uniqueresource ID.

If a cloned resource is not detected by the authorization service,execution advances to block 1118 where the authorization service gets anew authorization token for the role requested for the client resourceduring the registration process. The new authorization token may beacquired from an authorization token service associated with an onlineservice provider or the online service. The authorization token, andtimestamps for managing expiration of the authorization token may bestored in the resource authorization database. At block 1120, the newauthorization token is provided to the authorization agent. Theauthorization token may be signed or encrypted with the public key ofthe public-private key pair associated with the authorization agent.

FIG. 12 illustrates aspects of an example environment 1200 forimplementing aspects in accordance with various embodiments. As will beappreciated, although a web-based environment is used for purposes ofexplanation, different environments may be used, as appropriate, toimplement various embodiments. The environment includes an electronicclient device 1202, which can include any appropriate device operable tosend and/or receive requests, messages, or information over anappropriate network 1204 and, in some embodiments, convey informationback to a user of the device. Examples of such client devices includepersonal computers, cell phones, handheld messaging devices, laptopcomputers, tablet computers, set-top boxes, personal data assistants,embedded computer systems, electronic book readers, and the like. Thenetwork can include any appropriate network, including an intranet, theInternet, a cellular network, a local area network, a satellite networkor any other such network and/or combination thereof. Components usedfor such a system can depend at least in part upon the type of networkand/or environment selected. Many protocols and components forcommunicating via such a network are well known and will not bediscussed herein in detail. Communication over the network can beenabled by wired or wireless connections and combinations thereof. Inthis example, the network includes the Internet and/or other publiclyaddressable communications network, as the environment includes a webserver 1206 for receiving requests and serving content in responsethereto, although for other networks an alternative device serving asimilar purpose could be used as would be apparent to one of ordinaryskill in the art.

The illustrative environment includes at least one application server1208 and a data store 1210. It should be understood that there can beseveral application servers, layers or other elements, processes orcomponents, which may be chained or otherwise configured, which caninteract to perform tasks such as obtaining data from an appropriatedata store. Servers, as used herein, may be implemented in various ways,such as hardware devices or virtual computer systems. In some contexts,servers may refer to a programming module being executed on a computersystem. As used herein, unless otherwise stated or clear from context,the term “data store” refers to any device or combination of devicescapable of storing, accessing, and retrieving data, which may includeany combination and number of data servers, databases, data storagedevices, and data storage media, in any standard, distributed, virtual,or clustered environment. The application server can include anyappropriate hardware, software, and firmware for integrating with thedata store as needed to execute aspects of one or more applications forthe client device, handling some or all of the data access and businesslogic for an application. The application server may provide accesscontrol services in cooperation with the data store and is able togenerate content including, but not limited to, text, graphics, audio,video, and/or other content usable to be provided to the user, which maybe served to the user by the web server in the form of HyperText MarkupLanguage (“HTML”), Extensible Markup Language (“XML”), JavaScript,Cascading Style Sheets (“CSS”), JavaScript Object Notation (JSON),and/or another appropriate client-side structured language. Contenttransferred to a client device may be processed by the client device toprovide the content in one or more forms including, but not limited to,forms that are perceptible to the user audibly, visually, and/or throughother senses. The handling of all requests and responses, as well as thedelivery of content between the client device 1202 and the applicationserver 1208, can be handled by the web server using PHP: HypertextPreprocessor (“PHP”), Python, Ruby, Perl, Java, HTML, XML, JSON, and/oranother appropriate server-side structured language in this example.Further, operations described herein as being performed by a singledevice may, unless otherwise clear from context, be performedcollectively by multiple devices, which may form a distributed and/orvirtual system.

The data store 1210 can include several separate data tables, databases,data documents, dynamic data storage schemes and/or other data storagemechanisms and media for storing data relating to a particular aspect ofthe present disclosure. For example, the data store illustrated mayinclude mechanisms for storing production data 1212 and user information1216, which can be used to serve content for the production side. Thedata store also is shown to include a mechanism for storing log data1214, which can be used for reporting, analysis or other such purposes.It should be understood that there can be many other aspects that mayneed to be stored in the data store, such as page image information andaccess rights information, which can be stored in any of the abovelisted mechanisms as appropriate or in additional mechanisms in the datastore 1210. The data store 1210 is operable, through logic associatedtherewith, to receive instructions from the application server 1208 andobtain, update or otherwise process data in response thereto. Theapplication server 1208 may provide static, dynamic, or a combination ofstatic and dynamic data in response to the received instructions.Dynamic data, such as data used in web logs (blogs), shoppingapplications, news services, and other such applications may begenerated by server-side structured languages as described herein or maybe provided by a content management system (“CMS”) operating on, orunder the control of, the application server. In one example, a user,through a device operated by the user, might submit a search request fora certain type of item. In this case, the data store might access theuser information to verify the identity of the user and can access thecatalog detail information to obtain information about items of thattype. The information then can be returned to the user, such as in aresults listing on a web page that the user is able to view via abrowser on the client device 1202. Information for a particular item ofinterest can be viewed in a dedicated page or window of the browser. Itshould be noted, however, that embodiments of the present disclosure arenot necessarily limited to the context of web pages, but may be moregenerally applicable to processing requests in general, where therequests are not necessarily requests for content.

Each server typically will include an operating system that providesexecutable program instructions for the general administration andoperation of that server and typically will include a computer-readablestorage medium (e.g., a hard disk, random access memory, read onlymemory, etc.) storing instructions that, when executed (i.e., as aresult of being executed) by a processor of the server, allow the serverto perform its intended functions.

The environment, in one embodiment, is a distributed and/or virtualcomputing environment utilizing several computer systems and componentsthat are interconnected via communication links, using one or morecomputer networks or direct connections. However, it will be appreciatedby those of ordinary skill in the art that such a system could operateequally well in a system having fewer or a greater number of componentsthan are illustrated in FIG. 12. Thus, the depiction of the system 1200in FIG. 12 should be taken as being illustrative in nature and notlimiting to the scope of the disclosure.

The various embodiments further can be implemented in a wide variety ofoperating environments, which in some cases can include one or more usercomputers, computing devices or processing devices which can be used tooperate any of a number of applications. User or client devices caninclude any of a number of computers, such as desktop, laptop, or tabletcomputers running a standard operating system, as well as cellular,wireless, and handheld devices running mobile software and capable ofsupporting a number of networking and messaging protocols. Such a systemalso can include a number of workstations running any of a variety ofcommercially available operating systems and other known applicationsfor purposes such as development and database management. These devicesalso can include other electronic devices, such as dummy terminals,thin-clients, gaming systems, and other devices capable of communicatingvia a network. These devices also can include virtual devices such asvirtual machines, hypervisors, and other virtual devices capable ofcommunicating via a network.

Various embodiments of the present disclosure utilize at least onenetwork that would be familiar to those skilled in the art forsupporting communications using any of a variety of commerciallyavailable protocols, such as Transmission Control Protocol/InternetProtocol (“TCP/IP”), User Datagram Protocol (“UDP”), protocols operatingin various layers of the Open System Interconnection (“OSI”) model, FileTransfer Protocol (“FTP”), Universal Plug and Play (“UpnP”), NetworkFile System (“NFS”), Common Internet File System (“CIFS”), andAppleTalk. The network can be, for example, a local area network, awide-area network, a virtual private network, the Internet, an intranet,an extranet, a public switched telephone network, an infrared network, awireless network, a satellite network, and any combination thereof. Insome embodiments, connection-oriented protocols may be used tocommunicate between network endpoints. Connection-oriented protocols(sometimes called connection-based protocols) are capable oftransmitting data in an ordered stream. Connection-oriented protocolscan be reliable or unreliable. For example, the TCP protocol is areliable connection-oriented protocol. Asynchronous Transfer Mode(“ATM”) and Frame Relay are unreliable connection-oriented protocols.Connection-oriented protocols are in contrast to packet-orientedprotocols such as UDP that transmit packets without a guaranteedordering.

In embodiments utilizing a web server, the web server can run any of avariety of server or mid-tier applications, including Hypertext TransferProtocol (“HTTP”) servers, FTP servers, Common Gateway Interface (“CGI”)servers, data servers, Java servers, Apache servers, and businessapplication servers. The server(s) also may be capable of executingprograms or scripts in response to requests from user devices, such asby executing one or more web applications that may be implemented as oneor more scripts or programs written in any programming language, such asJava®, C, C#, or C++, or any scripting language, such as Ruby, PHP,Perl, Python or TCL, as well as combinations thereof. The server(s) mayalso include database servers, including without limitation thosecommercially available from Oracle®, Microsoft®, Sybase and IBM® as wellas open-source servers such as MySQL, Postgres, SQLite, MongoDB, and anyother server capable of storing, retrieving, and accessing structured orunstructured data. Database servers may include table-based servers,document-based servers, unstructured servers, relational servers,non-relational servers, or combinations of these and/or other databaseservers.

The environment can include a variety of data stores and other memoryand storage media as discussed above. These can reside in a variety oflocations, such as on a storage medium local to (and/or resident in) oneor more of the computers or remote from any or all of the computersacross the network. In a particular set of embodiments, the informationmay reside in a storage-area network (“SAN”) familiar to those skilledin the art. Similarly, any necessary files for performing the functionsattributed to the computers, servers or other network devices may bestored locally and/or remotely, as appropriate. Where a system includescomputerized devices, each such device can include hardware elementsthat may be electrically coupled via a bus, the elements including, forexample, at least one central processing unit (“CPU” or “processor”), atleast one input device (e.g., a mouse, keyboard, controller, touchscreen, or keypad) and at least one output device (e.g., a displaydevice, printer, or speaker). Such a system may also include one or morestorage devices, such as disk drives, optical storage devices, andsolid-state storage devices such as random access memory (“RAM”) orread-only memory (“ROM”), as well as removable media devices, memorycards, flash cards, etc.

Such devices also can include a computer-readable storage media reader,a communications device (e.g., a modem, a network card (wireless orwired), an infrared communication device, etc.), and working memory asdescribed above. The computer-readable storage media reader can beconnected with, or configured to receive, a computer-readable storagemedium, representing remote, local, fixed, and/or removable storagedevices as well as storage media for temporarily and/or more permanentlycontaining, storing, transmitting, and retrieving computer-readableinformation. The system and various devices also typically will includea number of software applications, modules, services, or other elementslocated within at least one working memory device, including anoperating system and application programs, such as a client applicationor web browser. In addition, customized hardware might also be usedand/or particular elements might be implemented in hardware, software(including portable software, such as applets), or both. Further,connection to other computing devices such as network input/outputdevices may be employed.

Storage media and computer readable media for containing code, orportions of code, can include any appropriate media known or used in theart, including storage media and communication media, such as, but notlimited to, volatile and non-volatile, removable and non-removable mediaimplemented in any method or technology for storage and/or transmissionof information such as computer readable instructions, data structures,program modules or other data, including RAM, ROM, Electrically ErasableProgrammable Read-Only Memory (“EEPROM”), flash memory or other memorytechnology, Compact Disc Read-Only Memory (“CD-ROM”), digital versatiledisk (DVD) or other optical storage, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices or any othermedium which can be used to store the desired information and which canbe accessed by the system device. Based on the disclosure and teachingsprovided herein, a person of ordinary skill in the art will appreciateother ways and/or methods to implement the various embodiments.

Note that the term “digital signature” includes any information usableto cryptographically verify authenticity of a message includinginformation generated using an RSA-based digital scheme (such asRSA-PSS), the digital signature algorithm (DSA) and the elliptic curvedigital signature algorithm, the ElGamal signature scheme, the Schnorrsignature scheme, the Pointcheval-Stern signature algorithm, the Rabinsignature algorithm, pairing-based digital signature schemes (such asthe Boneh-Lynn-Schacham signature scheme), undeniable digital signatureschemes, and others. Further, message authentication codes (such ashash-based message authentication codes (HMACs), keyed cryptographichash functions, and other types of information may also be used asdigital signatures.

In various embodiments, data objects such as digital signatures may becryptographically verifiable. In one example, cryptographicallyverifiable data objects are created to be cryptographically verifiableby the system to which the data object is to be provided or anothersystem that operates in conjunction with the system to which the dataobject is to be provided. For example, the data object may be encryptedso as to be decryptable by the system that will cryptographically verifythe data object, where the ability to decrypt the data object serves ascryptographic verification of the data object. As another example, thedata object may be digitally signed (thereby producing a digitalsignature of the data object) such that the digital signature isverifiable by the system that will cryptographically verify the dataobject. In other examples, both encryption and digital signatures areused for cryptographic verifiability and/or security. The key used toencrypt and/or digitally sign the data object may vary in accordancewith various embodiments and the same key is not necessarily used forboth encryption and digital signing, where applicable. In someembodiments, a key used to encrypt the data object is a public key of apublic/private key pair where the private key of the key pair ismaintained securely by the system to which the data object is to beprovided, thereby enabling the system to decrypt the data object usingthe private key of the key pair. Using the public key to encrypt thedata object may include generating a symmetric key, using the symmetrickey to encrypt the data object, and encrypting the symmetric key usingthe public key, where the encrypted symmetric key is provided to asystem with the encrypted data object to enable the system to use thecorresponding private key to decrypt the symmetric key and use thedecrypted symmetric key to decrypt the data object. Further, in someembodiments, the data object is digitally signed using a private key ofa public/private key pair corresponding to the computer system thatencrypts and/or digitally signs the data object (e.g., a user device).For example, an application may be provisioned with the private key andthe data object may include a certificate for the private key for use bya system for verification of the digital signature of the data object.Other variations, including variations where a symmetric key sharedbetween the user computer and the system that cryptographically verifiesthe data object can be used to encrypt and/or digitally sign the dataobject.

Note that a system is said to be configured to trust a publiccryptographic key if logic with which the system is configured tooperate is dependent on whether an attempt to verify a digital signaturewith the public cryptographic key is successful. Similarly, a system issaid to be configured to trust a symmetric cryptographic key if logicwith which the system is configured to operate is dependent on whetheran attempt to verify a digital signature with the symmetriccryptographic key is successful.

Generally, embodiments of the present disclosure may use variousprotocols, such as a SSL or TLS protocol and extensions thereto, such asdefined in Request for Comments (RFC) 2246, RFC 2595, RFC 2712, RFC2817, RFC 2818, RFC 3207, RFC 3268, RFC 3546, RFC 3749, RFC 3943, RFC4132, RFC 4162, RFC 4217, RFC 4279, RFC 4347, RFC 4366, RFC 4492, RFC4680, RFC 4681, RFC 4785, RFC 5054, RFC 5077, RFC 5081, RFC 5238, RFC5246, RFC 5288, RFC 5289, RFC 5746, RFC 5764, RFC 5878, RFC 5932, RFC6066, RFC 6083, RFC 6091, RFC 6176, RFC 6209, RFC 6347, RFC 6367, RFC6460, RFC 6655, RFC 7027, and RFC 7366, which are incorporated herein byreference, to establish encrypted communications sessions. Otherprotocols implemented below the application layer of the Open SystemsInterconnect (OSI) model may also be used and/or adapted to utilizetechniques described herein. It should be noted that the techniquesdescribed herein are adapatable to other protocols such as the Real TimeMessaging Protocol (RTMP), the Point-to-Point Tunneling Protocol (PPTP),the Layer 2 Tunneling Protocol, various virtual private network (VPN)protocols, Internet Protocol Security (e.g., as defined in RFC 1825through 1829, RFC 2401, RFC 2412, RFC 4301, RFC 4303, and RFC 4309), andother protocols, such as protocols for secure communication that includea handshake.

In the preceding and following description, various techniques aredescribed. For purposes of explanation, specific configurations anddetails are set forth in order to provide a thorough understanding ofpossible ways of implementing the techniques. However, it will also beapparent that the techniques described below may be practiced indifferent configurations without the specific details. Furthermore,well-known features may be omitted or simplified to avoid obscuring thetechniques being described.

The specification and drawings are, accordingly, to be regarded in anillustrative rather than a restrictive sense. It will, however, beevident that various modifications and changes may be made thereuntowithout departing from the broader spirit and scope of the invention asset forth in the claims.

Other variations are within the spirit of the present disclosure. Thus,while the disclosed techniques are susceptible to various modificationsand alternative constructions, certain illustrated embodiments thereofare shown in the drawings and have been described above in detail. Itshould be understood, however, that there is no intention to limit theinvention to the specific form or forms disclosed, but on the contrary,the intention is to cover all modifications, alternative constructions,and equivalents falling within the spirit and scope of the invention, asdefined in the appended claims.

The use of the terms “a” and “an” and “the” and similar referents in thecontext of describing the disclosed embodiments (especially in thecontext of the following claims) are to be construed to cover both thesingular and the plural, unless otherwise indicated herein or clearlycontradicted by context. The terms “comprising,” “having,” “including,”and “containing” are to be construed as open-ended terms (i.e., meaning“including, but not limited to,”) unless otherwise noted. The term“connected,” when unmodified and referring to physical connections, isto be construed as partly or wholly contained within, attached to, orjoined together, even if there is something intervening. Recitation ofranges of values herein are merely intended to serve as a shorthandmethod of referring individually to each separate value falling withinthe range, unless otherwise indicated herein and each separate value isincorporated into the specification as if it were individually recitedherein. The use of the term “set” (e.g., “a set of items”) or “subset”unless otherwise noted or contradicted by context, is to be construed asa nonempty collection comprising one or more members. Further, unlessotherwise noted or contradicted by context, the term “subset” of acorresponding set does not necessarily denote a proper subset of thecorresponding set, but the subset and the corresponding set may beequal.

Conjunctive language, such as phrases of the form “at least one of A, B,and C,” or “at least one of A, B and C,” unless specifically statedotherwise or otherwise clearly contradicted by context, is otherwiseunderstood with the context as used in general to present that an item,term, etc., may be either A or B or C, or any nonempty subset of the setof A and B and C. For instance, in the illustrative example of a sethaving three members, the conjunctive phrases “at least one of A, B, andC” and “at least one of A, B and C” refer to any of the following sets:{A}, {B}, {C}, {A, B}, {A, C}, {B, C}, {A, B, C}. Thus, such conjunctivelanguage is not generally intended to imply that certain embodimentsrequire at least one of A, at least one of B and at least one of C eachto be present.

Operations of processes described herein can be performed in anysuitable order unless otherwise indicated herein or otherwise clearlycontradicted by context. Processes described herein (or variationsand/or combinations thereof) may be performed under the control of oneor more computer systems configured with executable instructions and maybe implemented as code (e.g., executable instructions, one or morecomputer programs or one or more applications) executing collectively onone or more processors, by hardware or combinations thereof. The codemay be stored on a computer-readable storage medium, for example, in theform of a computer program comprising a plurality of instructionsexecutable by one or more processors. The computer-readable storagemedium may be non-transitory. In some embodiments, the code is stored onset of one or more non-transitory computer-readable storage media havingstored thereon executable instructions that, when executed (i.e., as aresult of being executed or in the course of being executed) by one ormore processors of a computer system, cause the computer system toperform operations described herein. The set of non-transitorycomputer-readable storage media may comprise multiple non-transitorycomputer-readable storage media and one or more of individualnon-transitory storage media of the multiple non-transitorycomputer-readable storage media may lack all of the code while themultiple non-transitory computer-readable storage media collectivelystore all of the code. Further, in some examples, the executableinstructions are executed such that different instructions are executedby different processors. As an illustrative example, a non-transitorycomputer-readable storage medium may store instructions. A main CPU mayexecute some of the instructions and a graphics processor unit mayexecute other of the instructions. Generally, different components of acomputer system may have separate processors and different processorsmay execute different subsets of the instructions.

Accordingly, in some examples, computer systems are configured toimplement one or more services that singly or collectively performoperations of processes described herein. Such computer systems may, forinstance, be configured with applicable hardware and/or software thatenable the performance of the operations. Further, computer systems thatimplement various embodiments of the present disclosure may, in someexamples, be single devices and, in other examples, be distributedcomputer systems comprising multiple devices that operate differentlysuch that the distributed computer system performs the operationsdescribed herein and such that a single device may not perform alloperations.

The use of any and all examples, or exemplary language (e.g., “such as”)provided herein, is intended merely to better illuminate embodiments ofthe invention and does not pose a limitation on the scope of theinvention unless otherwise claimed. No language in the specificationshould be construed as indicating any non-claimed element as essentialto the practice of the invention.

Embodiments of this disclosure are described herein, including the bestmode known to the inventors for carrying out the invention. Variationsof those embodiments may become apparent to those of ordinary skill inthe art upon reading the foregoing description. The inventors expectskilled artisans to employ such variations as appropriate and theinventors intend for embodiments of the present disclosure to bepracticed otherwise than as specifically described herein. Accordingly,the scope of the present disclosure includes all modifications andequivalents of the subject matter recited in the claims appended heretoas permitted by applicable law. Moreover, any combination of theabove-described elements in all possible variations thereof isencompassed by the scope of the present disclosure unless otherwiseindicated herein or otherwise clearly contradicted by context.

All references, including publications, patent applications, andpatents, cited herein are hereby incorporated by reference to the sameextent as if each reference were individually and specifically indicatedto be incorporated by reference and were set forth in its entiretyherein.

What is claimed is:
 1. A computer-implemented method comprising: underthe control of one or more computer systems configured with executableinstructions, receiving, from a client, a registration request, theregistration request specifying a security role to be granted to aclient resource by an online service; determining that credentialssubmitted with the registration request are valid; authorizing theregistration request; generating an activation code for the registrationrequest; generating a resource ID for the client resource; storingsufficient information to identify the activation code and sufficientinformation to identify the resource ID; returning the activation codeto the client; causing an authorization agent to be installed on theclient resource; receiving an activation request from the authorizationagent, the activation request including the resource ID and theactivation code; acquiring, from an authorization token service that isassociated with the online service, an authorization token that allowsthe client resource to use the online service in accordance with thesecurity role; and providing the authorization token to theauthorization agent.
 2. The computer-implemented method of claim 1further comprising: determining that an expiration has elapsed or thatthe activation code has been provided with a previous activationrequest; and invalidating the activation code based at least in part ondetermining that the expiration has elapsed or that the activation codehas been provided with a previous activation request.
 3. Thecomputer-implemented method of claim 1, wherein: the activation requestincludes a public key of a public-private key pair; the activationrequest is digitally signed using a private key associated with thepublic-private key pair; and the public key is retained.
 4. Thecomputer-implemented method of claim 1 further comprising: receiving apseudo-unique resource ID with the activation request, the pseudo-uniqueresource ID generated by the authorization agent to be unique to theclient resource; and determining that the client resource is a clonedresource based at least in part on the pseudo-unique resource ID.
 5. Asystem comprising at least one computing device that implements anauthorization service, wherein the authorization service: receives aregistration request to register a client resource associated with aclient with an online service; authorizes the registration request basedat least in part on credentials associated with the client; provides anactivation code to the client in response to the registration request;receives, from the client resource, an activation request that includesthe activation code; acquires an authorization token that allows aservice request to be fulfilled by the online service; and provides theauthorization token to the client resource.
 6. The system of claim 5,wherein the authorization service further: receives an expiration withthe registration request; stores the expiration; determines that theactivation code is expired by comparing the expiration to a currenttime; and invalidates the activation code.
 7. The system of claim 5,wherein a service management interface installs an authorization agenton the client resource.
 8. The system of claim 5, wherein theauthorization service further: receives a pseudo-unique resource ID withthe activation request, the pseudo-unique resource ID based at least inpart on a processor ID of the client resource, a device serial number ofthe client resource, or a network address of a network interfaceassociated with the client resource; and determines that the clientresource has not been replicated from a parent client resource based atleast in part on the pseudo-unique resource ID.
 9. The system of claim5, wherein the authorization service further: receives a public key of apublic-private key pair with the activation request; and verifies adigital signature on the activation request using the public key. 10.The system of claim 5, wherein the authorization service further:determines that a difference between a timestamp on the activationrequest and a current time exceeds a timeout value; and determines thatthe activation request has expired and denies the activation request.11. The system of claim 5, wherein the online service: receives aservice request that includes a timestamp; and denies the servicerequest if the difference between the timestamp and the time the servicerequest is received is greater than a threshold amount of time.
 12. Thesystem of claim 5, wherein: the authorization token is acquired from anauthorization token service that is associated with an online serviceprovider; the online service provider provides a plurality of onlineservices; and the authorization token is usable with more than oneonline service of the plurality of online services.
 13. A non-transitorycomputer-readable storage medium having stored thereon executableinstructions that, in the course of being executed by one or moreprocessors of a client resource, cause the client resource to at least:acquire an activation code and a resource identifier, the activationcode and the resource identifier provided by an authorization servicethat is associated with an online service provider; generate apublic-private key pair that includes a public key and a private key;generate a pseudo-unique resource identifier for the client resource;submit an activation command to the authorization service, theactivation command including the public key, the pseudo-unique resourceidentifier, the resource identifier, the activation code, and a digitalsignature generated with the private key; and receive an authorizationtoken in response to the activation command.
 14. The non-transitorycomputer-readable storage medium of claim 13, wherein the instructionsfurther comprise instructions that, in the course of being executed bythe one or more processors, cause the client resource to: submit aservice request to an online service provided by the online serviceprovider, the service request including the authorization token.
 15. Thenon-transitory computer-readable storage medium of claim 14, wherein theinstructions further comprise instructions that, in the course of beingexecuted by the one or more processors, cause the client resource to:determine that the service request was denied by the online service;submit a refresh request to the authorization service that causes theauthorization service to issue a new authorization token; and receive anew authorization token from the authorization service.
 16. Thenon-transitory computer-readable storage medium of claim 15, wherein theinstructions that cause the client resource to determine that theservice request was denied further include instructions that cause theclient resource to: determine that the client resource is a clonedresource; and register the client resource using a new resourceidentifier.
 17. The non-transitory computer-readable storage medium ofclaim 15, wherein the refresh request includes a digital signaturegenerated using the private key.
 18. The non-transitorycomputer-readable storage medium of claim 13, wherein the instructionsfurther comprise instructions that, in the course of being executed bythe one or more processors, cause the client resource to: receive aservice request from an online service provided by the online serviceprovider; and fulfill the service request.
 19. The non-transitorycomputer-readable storage medium of claim 14, wherein the servicerequest is submitted to the online service over a computer network via atransport layer security (“TLS”) connection.
 20. The non-transitorycomputer-readable storage medium of claim 14, wherein the instructionsfurther comprise instructions that, in the course of being executed bythe one or more processors, cause the client resource to: generate asequence number associated with the service request; submit the sequencenumber to the authorization service with the service request; andreceive an indication from the authorization service that the clientresource is a cloned resource, the indication based at least in part onthe sequence number.